Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1418

reference
693-tree-1
name
1418
tree-preservation-order

undefined

693-tpo-1
uprn
address-text
point
POINT (-1.011549 50.881916)
geometry
MULTIPOLYGON (((-1.011492 50.881910,-1.011495 50.881921,-1.011503 50.881931,-1.011515 50.881939,-1.011531 50.881945,-1.011548 50.881947,-1.011566 50.881945,-1.011582 50.881940,-1.011595 50.881932,-1.011603 50.881922,-1.011606 50.881911,-1.011603 50.881900,-1.011596 50.881890,-1.011583 50.881882,-1.011567 50.881877,-1.011550 50.881875,-1.011532 50.881876,-1.011516 50.881881,-1.011504 50.881889,-1.011495 50.881899,-1.011492 50.881910)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL